BBS Toolkit

home *** CD-ROM | disk | FTP | other *** search

/ BBS Toolkit / BBS Toolkit.iso / pc_board / pcbfx11.zip / PCBFX.DOC < prev next >

Wrap

Text File | 1992-04-03 | 50KB | 1,158 lines

------------------------------------------------------------------ | | | | | | | | | PCBFX Version 1.1 | | | | PCB File Transfer Profile Information Door | | | | | | For | | | | PCBoard Versions 14.5 & 14.5a | | | | | | Quickly scans DOWNLOAD.TXT and reports: | | | | + Number of times a file has been download | | + Who uploaded the file | | + The date of the last download | | + The date of the upload | | + The date where the scan begins | | | | All scan data is displayed in a Sysop configurable text | | file display using information macros for data fields. | | | | * All display options are Sysop configurable. * | | * Security levels for all display fields. * | | * Conference blocking list for Who Uploaded info. * | | | | Special Sysop level for Zippy text scans | | | | Seamless Appearance when used as a "shelled-to" door | | | | | | PCBFX Version 1.1 | | | | (C) Copyright 1992 Yandell Computer Services | | | | 12121 Little Road - Bldg. 303 - Suite 212 | | Hudson, FL 34667 | | | | DATA -- (813) 842-8099 (HST) | | | | | | April 3, 1992 | | | | | | | ------------------------------------------------------------------ -------------------------------------------------------------------- PCBFX -------------------------------------------------------------------- TABLE OF CONTENTS Page ----------------- ---- INTRODUCTION ------------ 1.0 What Is PCBFX 3 1.1 Multi-Nodes, Networks, Multi-taskers 3 INSTALLING PCBFX ---------------- 2.0 Preliminaries 4 2.1 Configuring PCBoard Door Files 4 2.2 Setting Up Door Batch Files 5 2.3 Running FXSETUP and Creating PCBFX.CNF 6-10 2.4 Setting Up .CNF files for Multi-Language Use 11 2.5 Setting up BLOCK.DAT 11 2.6 Setting Up the Profile INFO Display File 12 RUN-TIME CONSIDERATIONS ----------------------- 3.0 Notes Regarding File Profiles 13 3.1 Notes Regarding Sysop Zippy Scans 14 3.2 Notes Regarding Local Command Line Use 14 MISCELLANEOUS ------------- 4.0 Sysop Function Keys 15 4.1 Technical Notes 15 4.2 Where To Receive Assistance 15 4.3 Error Messages 15 4.4 Caller Log Entries 16 4.5 Disclaimer and Warranty 16 4.6 License to Use PCBFX 17 4.7 Revision History 17 REGISTRATION ------------ 5.0 Registering PCBFX 17 5.1 Register With CONFIDENCE - Author Information 18 -------------------------------------------------------------------- Page 3 PCBFX Page 3 -------------------------------------------------------------------- 1.0 What is PCBFX ------------------ PCBFX (PCBoard File Xfer) provides a file transfer "PROFILE" using PCBoard's DOWNLOAD.TXT file. Information such as the number of downloads, who uploaded, the date of the last download, the date of the upload, and the date at which the profile scan begins can be displayed to the caller. ALL of this information is displayed in a text file, so that both the content and appearance of what the caller sees in the profile report is 100% CONFIGURABLE by the Sysop. PCBFX also provides the ability for those at or above a certain security level (Sysops or co-Sysops) to perform "Zippy" text scans on DOWNLOAD.TXT. Typical scans may be for user names, file names, and possible dates of activity. The report is formatted in an easy to read display and non-essential info from DOWNLOAD.TXT is removed. A caller cannot retrieve a profile on a file if: (A) The file does not physically exists on the system. (B) The caller lacks sufficient access to download the file. (C) The file is password protected and the caller cannot provide it. For the purposes above, PCBFX is highly integrated with PCBoard and reads such PCBoard files as the conference list (CNAMES), and the proper conference download path list (DLPATH.LST). The security file (FSEC) is read to determine the security a caller would need to download the file, and to see if a file is password protected. If a file requires a password, PCBFX will ask the caller in the same fashion as PCBoard. All of the profile items may have their own security attached to them so that only certain callers are allowed to see certain items. A conference list can be created to block the "who uploaded" field. This is useful where there are conference files and this information should not be available to anyone. A default uploader name may be displayed if there is none found in DOWNLOAD.TXT. This could be useful for Sysops who manually add many files to their systems. PCBFX is DESQview aware. PCBFX works with non-standard com ports automatically. 1.1 Multi-nodes, networks, multi-taskers ----------------------------------------- PCBFX has been developed in a networked environment. All multi-node features are thoroughly tested on our own multi-node PCBoard system. PCBFX's primary beta test site is a twenty node PCBoard system. PCBFX is DESQview aware. It is automatically detected, screen and keyboard I/O are "well behaved", and time slices are given back to other applications while PCBFX is idle. -------------------------------------------------------------------- Page 4 PCBFX Page 4 -------------------------------------------------------------------- 2.0 Preliminaries ------------------ Create a directory or subdirectory where you normally place doors. Extract the entire contents of PCBFX11.ZIP into this location. All files enclosed in PCBFX11.ZIP must be located in the same location with PCBFX.EXE in order for the program to function properly. 2.1 Configuring PCBoard Door Files ----------------------------------- The intent in PCBFX is to install it as an "add-on" command on the PCBoard main menu, rather than in a door menu. First decide what you would like this new "command" to be. Some examples: FX - File Xfers FI - File Information FP - File Profile Install a door called FX or whatever you decide to call it into your DOORS.LST file using PCBSETUP. Answer the following questions: USER DOOR Filename Password Sec Login SYS SYS Shell Path to DOOR Files -------- -------- --- ----- --- --- ----- ------------------ #) FX 10 N Y N Y (if appropriate) A password would usually not be required for your FX door. A USERS.SYS file MUST be created. PCBFX will not operate without it. A DOOR.SYS file is NOT needed and should not be created. If running PCBoard 14.5a, SHELLing is HIGHLY recommended because it greatly increases the speed at which PCBoard returns when the caller exits from PCBFX. PCBFX has been specifically designed as a "Shell" door. Setting up PCBFX as a "swapped shell" door is not recommended unless it is needed due to severe memory limitations. If you have different DOORS.LST files in your conferences, you will need to configure the FX door in them also. It is up to the individual Sysop as to whether or not to place the FX command in the doors menu, or as a command on the main menu, or both. The recommended usage is to place FX (or whatever the command will be called) on the main menu and not in the doors menu. -------------------------------------------------------------------- Page 5 PCBFX Page 5 -------------------------------------------------------------------- 2.2 Setting up door batch files -------------------------------- The purpose of this section is to explain the command line calling syntax for PCBFX. Please refer to the PCBoard manual for a more complete discussion on door batch file installation. If you have named the door FX (recommended) the following examples would be the contents of your door file named FX (NOTE: do NOT place an extension such as .BAT on the FX file). *PREFERRED METHOD* (fast load!) ------------------------------- @echo off C:\PCBFX\PCBFX.EXE PCBFX.CNF C:\PCB ------------------ --------- ------ | | |-> This node's home directory. | | | | | ---------> The name of the configuration | file. Enter a file NAME only. | NEVER place a location here. | -------> The executable file name. Placing its location in-line as shown results in MUCH faster response time in executing the door. The two lines above are all that is required to execute PCBFX when running as a shelled-to door in PCBoard 14.5a. If you are not running PCBoard 14.5a or you are not running PCBFX as a shelled-to door, add the call to BOARD.BAT as the third command in the door file. Do NOT end your door file with BOARD.BAT if running PCBFX as a shell-to door in PCBoard 14.5a. *OLD FASHIONED METHOD* (tried and true, but slow load) ------------------------------------------------------ @echo off d: cd\pcbfx PCBFX.EXE PCBFX.CNF C:\PCB c: ------ cd\pcb |-> This node's home directory. The above method will work fine with PCBFX. The only drawback is the slower loading time as a result of the changing of drives and directories in DOS. As with the "preferred method", only add BOARD.BAT to the end of the door file if you are NOT shelling to PCBFX in PCBoard 14.5a, or if you are running PCBoard 14.5. -------------------------------------------------------------------- Page 6 PCBFX Page 6 -------------------------------------------------------------------- 2.3 Running FXSETUP and creating PCBFX.CNF ------------------------------------------- Enclosed with PCBFX 1.1 is a file called FXSETUP.EXE. This file allows you to easily configure PCBFX configuration files. Only one PCBFX.CNF file is required for all nodes. Please refer to section 2.4 page 11 for information on creating PCBFX.CNF files for multi- language use. To start FXSETUP.EXE, enter FXSETUP PCBFX.CNF at your DOS prompt (PCBFX.CNF would be the appropriate configuration file). Each parameter in FXSETUP is described on the following pages. * Your PCBFX Registration Number --------------------------------- This is the number received when PCBFX is registered. Registration causes the PCBFX [ UNREGISTERED COPY ] message and the brief delay at program termination to disappear. This message is not replaced with your board name or anything else. The entire line completely disappears for a true, seamless, "looks like PCBoard" process if running as a shelled-to door in PCBoard 14.5a. * Loc\Name of DOWNLOAD.TXT File -------------------------------- This is the LOCATION AND NAME of the DOWNLOAD.TXT file. Setting the location and name in a PCBFX configuration file accomplishes several tasks. If DOWNLOAD.TXT is renamed, shortened, or otherwise changed in a system "event", this allows another (original) file to be used. Use the location and name in PCBSETUP, option C (File Locations 2), in the "Name/Loc of Transfer Summary File" parameter if this file is not being changed in a system "event" (or at any other time). Use the location and name of an original copy of this file if the file in the above parameter is changed by another process. Setting this parameter in a PCBFX configuration file also allows PCBFX to run in a command line local mode without having to read PCBoard files to determine the location and name of DOWNLOAD.TXT. Section 2.3 continues on the next page -------------------------------------------------------------------- Page 7 PCBFX Page 7 -------------------------------------------------------------------- 2.3 Running FXSETUP and creating PCBFX.CNF (continued) ------------------------------------------------------- * Security to Show Date of First DOWNLOAD.TXT Entry ---------------------------------------------------- The caller must have this security or greater for the parameter indicated below to be displayed. Transfer information for file: Scanning all transfers after : @DWNTXTDATE@ Name of person who sent file : Date the file was uploaded : Number of times downloaded : Date file was last downloaded: If the caller is below this level, the above information macro will be changed to "Unavailable" when displayed to the caller. * Security to Show Who Uploaded -------------------------------- The caller must have this security or greater for the parameter indicated below to be displayed Transfer information for file: Scanning all transfers after : Name of person who sent file : @UPLOADNAME@ Date the file was uploaded : Number of times downloaded : Date file was last downloaded: If the caller is below this level, the above information macro will be changed to "Unavailable" when displayed to the caller. * Security to Show Upload Date ------------------------------- The caller must have this security or greater for the parameter indicated below to be displayed. Transfer information for file: Scanning all transfers after : Name of person who sent file : Date the file was uploaded : @UPLOADDATE@ Number of times downloaded : Date file was last downloaded: If the caller is below this level, the above information macro will be changed to "Unavailable" when displayed to the caller. Section 2.3 continues on the next page -------------------------------------------------------------------- Page 8 PCBFX Page 8 -------------------------------------------------------------------- 2.3 Running FXSETUP and creating PCBFX.CNF (continued) ------------------------------------------------------- * Security to Show Number of Downloads --------------------------------------- The caller must have this security or greater for the parameter indicated below to be displayed. Transfer information for file: Scanning all transfers after : Name of person who sent file : Date the file was uploaded : Number of times downloaded : @NUMBERDOWN@ Date file was last downloaded: If the caller is below this level, the above information macro will be changed to "Unavailable" when displayed to the caller. * Security to Show Last Download Date -------------------------------------- The caller must have this security or greater for the parameter indicated below to be displayed. Transfer information for file: Scanning all transfers after : Name of person who sent file : Date the file was uploaded : Number of times downloaded : Date file was last downloaded: @LASTDLDATE@ If the caller is below this level, the above information macro will be changed to "Unavailable" when displayed to the caller. * Security for Sysop Zippy Text Scans -------------------------------------- This is the security level needed for PCBFX to display the prompt that allows choosing between a (F)ile profile or a (Z)ippy scan. * This should be a security level used by Sysops and Co-Sysops only! If the caller is below this level, they are shown the configurable "File Profile" input prompt (which displays the INFO file). The Zippy text scan feature will not be available to these callers. If the caller is at or above this level, they will be given a choice as to whether to perform a Zippy text scan on the entire DOWNLOAD.TXT file, or File Profile scan of a single file's activity. Section 2.3 continues on the next page -------------------------------------------------------------------- Page 9 PCBFX Page 9 -------------------------------------------------------------------- 2.3 Running FXSETUP and creating PCBFX.CNF (continued) ------------------------------------------------------- * Default Uploader Name ------------------------ If upload information is not found in DOWNLOAD.TXT (or equivalent) a default name may be displayed. This is useful when many files are manually added to a system. The default uploader name will appear in this parameter: Transfer information for file: Scanning all transfers after : Name of person who sent file : @UPLOADNAME@ Date the file was uploaded : Number of times downloaded : Date file was last downloaded: To disable this default feature and have "Unavailable" display when no upload information is found, enter NONE in this parameter. * 'Who Uploaded' Conference Block List --------------------------------------- If a caller performs an 'FX' request in one of the conferences in this list, the "Name of person who sent file' (who uploaded) will not be displayed. This is to accommodate Sysops who have conferences that have special conference files where the uploader should not be known. Simply enter conference numbers separated by a comma (,) such as: 13,14,15,16,17,54,200,201,202 You may group a block of conferences together with a dash: 13-17,54,200-202 Both of the above examples would block the same conferences. IMPORTANT: If you have areas important enough that you feel you need to protect with this feature, then ALWAYS TEST ALL CONFERENCES that are included in the list. Section 2.3 continues on the next page -------------------------------------------------------------------- Page 10 PCBFX Page 10 -------------------------------------------------------------------- 2.3 Running FXSETUP and creating PCBFX.CNF (continued) ------------------------------------------------------- Compressed Filename Extension ----------------------------- The DEFAULT compressed filename extension is configured in the PCBFX configuration files. Setting this default in PCBFX files rather than reading this information from PCBoard system files allows this feature to be used in PCBFX's special Sysop local mode. When entering a filename for a 'File profile' this extension will be appended to the entry if an extension is omitted by the caller. The entry entered here should be the same entry for PCBFX as it is for PCBoard. If ZIP is the default extension for PCBoard, then ZIP be entered in this PCBFX parameter also. Activity to Track in CALLER Logs -------------------------------- You may select the activity to track in PCBoard CALLER files. * Profile executed on file (FILENAME.EXT) Enter (F) to have the above written to CALLER log files each time a caller performs a (F)ile Profile scan. * Zippy Scan for (text) Enter (A) (All) to have both File Profile scans and the above Zippy scan activity written to CALLER log files. Enter N for none if this tracking is not desired. The default (F)ile profile (only) tracking is how PCBFX v1.0 performed before this toggle was added in version 1.1. * File Prompt -------------- You may change PCBFX's File Profile input prompt. The default is: Filename for Transfer Profile (Enter)=none? What is entered here is exactly what PCBFX will display to the caller. See section 2.4 page 11 for instructions on how to make this prompt multi-language compatible. -------------------------------------------------------------------- Page 11 PCBFX Page 11 -------------------------------------------------------------------- 2.4 Setting up .CNF files for multi-language use ------------------------------------------------- To make the "File Prompt" text in PCBFX.CNF language compatible for a caller, simply create a duplicate PCBFX.CNF file except give it the appropriate EXTension. For instance with French, use French for this prompt in PCBFX.FRE and PCBFX will automatically use PCBFX.FRE instead of PCBFX.CNF as the configuration file. You do not need to worry about what PCBFX is passed in the door file. If passed PCBFX.CNF and the language is .FRE, PCBFX will look for PCBFX.FRE before using PCBFX.CNF. 2.5 Setting up BLOCK.DAT ------------------------- If there are files which you wish callers to be able to download, but would prefer the profile remain private, you may "block" those file names by placing them in a text file called BLOCK.DAT. With a text editor, edit BLOCK.DAT in the location with PCBFX.EXE. Simply enter the COMPLETE or WILDCARD file names of those files which may exist on your system yet you do not wish callers to see a profile for. Press enter (RETURN) after each name is entered in BLOCK.DAT so that each entry is on a new line. If you not not wish to use this feature then delete BLOCK.DAT. See figure 2.5 below for examples of names in BLOCK.DAT. ------------------------------------------------------------------ | Good examples Bad examples | | ------------- ------------ | | *.CAP PCBFX uses regular DOS .CAP | | READ*.* wildcard specs to see if READ* | | ALLFILES.ZIP a file is a match. If so, ALLFILES. | | it cannot be profiled. | ------------------------------------------------------------------ ---- Figure 2.5 ---- BLOCK.DAT must reside in the same location with PCBFX.EXE There is a limitation of 100 entries in BLOCK.DAT. This should be sufficient for any needs regarding this parameter. The entries in BLOCK.DAT will not be used when the following occurs: (A) PCBFX is running in its /L local command line mode. (B) The caller's security level meets the security level defined for the Sysop Zippy scan in FXSETUP. -------------------------------------------------------------------- Page 12 PCBFX Page 12 -------------------------------------------------------------------- 2.6 Setting Up the Profile INFO Display File --------------------------------------------- The text file called INFO is the heart and sole of PCBFX. It is what is displayed to the caller when a file profile request is made. All information provided is done with information @macros@ as described below, making the appearance and functionality of PCBFX 100% Sysop configurable. Two example files are included in PCBFX11.ZIP. They are INFO and INFO2. To see INFO2 used copy INFO to INFO1 then copy INFO2 to INFO. These examples plus the information below should provide enough details to allow you to customize an INFO file for your needs. @FILENAMEFX@ This will be replaced with the file name that the current profile request is for. The replacement is padded to 12 characters. @DWNTXTDATE@ This will be replaced with the date of the FIRST entry in DOWNLOAD.TXT. The replacement is padded to 12 characters. @UPLOADNAME@ This is the name of the person who uploaded the file or the "default uploader" name as supplied if uploader information is not found. The replacement is padded to 25 characters. @UPLOADDATE@ This is the date of the upload. The replacement is padded to 12 characters. @NUMBERDOWN@ This is the number of times the file was downloaded. The replacement is padded to 12 characters. @LASTDLDATE@ This is the last date the file was downloaded on. The replacement is padded to 12 characters. Any macros will replaced with "Unavailable" if the caller does not have security to view it (as defined in FXSETUP). The INFO file is additionally flexible by supporting the security file convention. If a caller is a level 30, and a file called INFO30 exists, it will be shown to the caller instead of the INFO file. Using this feature, you may create INFO files which do not even display the macros which a level cannot view (macros which would be replaced with "Unavailable" as described above). @CLS@ will clear the screen each time INFO is displayed. INFO supports PCBoard @X## color codes for utilizing color. Because PCBFX has been designed to be as small as possible for a "shell to" door, ANSI capabilities in this file were intentionally omitted, as well as support for the numerous PCBoard information macros. If multi-languages are in use, the appropriate extension will be added to the INFO file. If the language file exists, it will be used for the display to the caller. -------------------------------------------------------------------- Page 13 PCBFX Page 13 -------------------------------------------------------------------- 3.0 Notes regarding File Profiles ---------------------------------- If a caller does have the security for Sysop Zippy scans, they will only access the "File Prompt" as defined in FXSETUP. When PCBFX is called, it will immediately present this prompt to the caller. One file name may be passed to PCBFX from the PCBoard command line. For example, if you have named the command FX, then typing: FX FILENAME.ZIP will load PCBFX and cause it to immediately start a profile scan for FILENAME.ZIP. This process is handled automatically by PCBFX and PCBoard and requires no additional installation. If the extension is omitted from the file name, whether passing the name from PCBoard or entered at the File Profile prompt, the default extension for compressed files as defined with FXSETUP.EXE will be used by PCBFX. After a file name is entered, PCBFX will check to insure that it is a valid file name and could exist. File names which do not conform to DOS name conventions or which could be a DOS device will not be accepted. PCBFX will then scan the download path from PCBoard for the conference the caller requested the profile in. If the file does not (still) physically exist, the caller will be informed. If the caller does not have enough access to download a file in PCBoard they will also not be able to perform a profile on that file. If a file in PCBoard is password protected, PCBFX will require the caller to input the password before allowing the profile to proceed. If the caller is in a conference that has been included in the "conference block" list in FXSETUP, the 'who uploaded' information will be replaced with "Unavailable". The special /L local command line mode performs slightly differently than when running with PCBoard. When a profile is performed in the /L local mode, the files existence, password security, and like features are not performed. In this manner, the Sysop may retrieve a profile for a file which is no longer physically on the system. After each profile, the input prompt for another "Profile Filename" will appear. Pressing (Enter) alone at this prompt will return the caller to PCBoard. If the user has access to the Sysop Zippy function, they will be returned to the (F)ile profile, (Z)ippy scan selection prompt. -------------------------------------------------------------------- Page 14 PCBFX Page 14 -------------------------------------------------------------------- 3.1 Notes regarding Sysop Zippy scans -------------------------------------- It should be stressed again that is important to only allow Sysops and possibly co-Sysops the ability to use the Sysop Zippy text scan feature. Anyone who is at or above the security level set for this feature in FXSETUP will have the ability to view any and all of the entries in the DOWNLOAD.TXT file. If access to the Zippy scan is permitted or PCBFX is running in its special local mode, PCBFX will begin with a prompt asking whether to perform a (F)ile profile or a (Z)ippy command. After a subsequent profile or zippy search, the appropriate text input prompt will continue appearing until (Enter) alone is pressed which will return to the (F)ile profile or (Z)ippy prompt. Pressing (Enter) at this prompt will return to PCBoard. Sysops may use the Zippy scan to scan for a particular file name, a particular user name, or possibly any activity on a particular date. Do not use wildcards in the Zippy search. They are not required. If scanning for activity on a particular date, the following format must be used: MM-DD-YYYY. This is required to match the date format which is used in the DOWNLOAD.TXT file. If using PCBFX in color mode or in local /L mode on a color monitor, the results of the Zippy scan will be minimally colorized. Lines with found text which are UPLOADS will be yellow, and lines with found text which are downloads are light blue. The prompts for (F)ile profile-(Z)ippy scan, and the Zippy text input prompt were not made configurable as they were not designed for casual caller use and should only be used by the Sysop or knowledgeable co-Sysops. 3.2 Notes regarding local command line use ------------------------------------------- Create a batch file called FX.BAT (or whatever name you choose): C:\PCB\PCBFX PCBFX.CNF %1 /L Place FX.BAT (or whatever you name it) in your DOS path, and you will have a DOWNLOAD.TXT profiler and searcher at your fingertips at all times. Simply type FX FILENAME.ZIP to start PCBFX and immediately begin a profile scan of FILENAME.ZIP. For any other use, simply type FX and PCBFX will begin by asking whether or not you wish to for a (F)ile profile or (Z)ippy search. -------------------------------------------------------------------- Page 15 PCBFX Page 15 -------------------------------------------------------------------- 4.0 Sysop function keys ------------------------ PCBFX follows F3 (printer on/off), and F9 (display on/off) toggles from PCBoard. If F3 is on, PCBFX will print any information sent to the caller log to the printer also. If F9 is off, PCBFX will not write to the local screen. PCBFX will act on ALT-X and ALT-N requests from the Sysop. PCBFX will set the appropriate flag so that PCBoard will use it after the caller logs off (as if ALT-X or ALT-N had been set in PCBoard). 4.1 Technical notes -------------------- PCBFX has been designed to run specifically with PCBoard versions 14.5 and 14.5a. PCBFX will not run with earlier versions of PCBoard or with other brands of BBS software. PCBFX is not a "kit door" of any kind. PCBFX is an incorporation of the PCBFX application and the author's OWN door routines which have been carefully developed over the last FIVE years. It is a stand alone program which does not require any additional files for execution (other than those it is packaged with and those provided by PCBoard). Carrier is monitored by PCBFX. Should a caller drop carrier while in PCBFX they will be returned to PCBoard, which will detect the "no carrier" status and cycle appropriately. PCBFX works with non-standard com ports ,addresses, and IRQs. COM1 is address 3F8/IRQ 4. COM2 is address 2F8/IRQ 3. If a COM port other than 1 or 2 is used, PCBFX will use the address and IRQ information as indicated in PCBOARD.DAT for the node. At this time PCBFX does not support extended IRQ's above IRQ7. 4.2 Where to receive assistance -------------------------------- Yandell Computer Services (YCS) provides the following technical assistance for PCBFX: 813-842-8099 The YCS Support System. Available to all BBS Sysops. INSTANT on-line credit card registration and support system for YCS Shareware. All nodes are 14400 (HST). On-line 7 days per week, 24 hours per day. 4.3 Error messages ------------------- PCBFX gives verbose installation error messages, such as invalid paths. These messages appear and there is a short pause while they are displayed. -------------------------------------------------------------------- Page 16 PCBFX Page 16 -------------------------------------------------------------------- 4.4 Caller log entries ----------------------- PCBFX makes pertinent entries into the caller log as follows: * Profile executed on file (FILENAME.EXT) - Caller performed a profile on FILENAME.EXT (See NOTE #1 below). * Zippy Scan for (text) - A Zippy scan was performed for (text) (See NOTE #1 below). * (FILENAME.EXT) not found! - FILENAME.EXT was not physically found during a profile request. * (FILENAME.EXT) is an invalid filename! - File is not a valid DOS file name or is an illegal file name. * Transfer Profile is not permitted on (FILENAME.EXT) - FILENAME.EXT exists in BLOCK.DAT. * Insufficient security for Profiling (FILENAME.EXT) - Caller lacks access to download file as found in PCBoard FSEC. * Incorrect Profile Password for File (FILENAME.EXT) - FILENAME.EXT has password in FSEC and caller could not provide. Note #1 from above: This entry will be written only if the Sysop desires (as defined in the FXSETUP 'Activity to track' parameter). 4.5 Disclaimer and warranty ---------------------------- PCBFX is a shareware product. PCBFX may be uploaded to BBS systems as long as copyright notices are not removed and no changes are made to the program. There are no warranties, expressed or implied, for unregistered copies of PCBFX. Sysops who install PCBFX on their systems assume any and all liabilities for anything which may result as a consequence of running PCBFX. For registered copies of PCBFX, Yandell Computer Services warrants that PCBFX will perform as described in this documentation. In the event that PCBFX does not perform as specified, Yandell Computer Services may elect to fix PCBFX or refund the amount paid, if notified within 30 days of registration. Under no circumstances shall Yandell Computer Services or the author of PCBFX be liable for any loss of profit or any other damages, including but not limited to special, incidental, consequential, or other damages, arising out of the use or inability to use PCBFX. PCBoard is a registered trademark of Clark Development Co. Inc. DESQview is a registered trademark of Quarterdeck Office Systems. -------------------------------------------------------------------- Page 17 PCBFX Page 17 -------------------------------------------------------------------- 4.6 License to use PCBFX ------------------------- PCBFX is not "public domain" or "free" software. A limited license is granted to use and evaluate PCBFX for thirty days after initial installation. PCBFX must be registered if it is used after the initial thirty day evaluation period. A PCBFX registration may be used only on the original licensee's BBS system and only on nodes the original licensee owns and operates for their own purposes. If the original licensee leases or sells some or all of their nodes to another entity, those nodes will require their own PCBFX registration. PCBFX registrations are not transferable. A PCBFX registration is a license to use the PCBFX software on one (1) BBS System at a single location with as many nodes as the original licensee owns and operates at THAT location. When the licensee owns and operates other BBS' in other locations, each location will require a separate PCBFX registration. If PCBFX has not been registered after 30 days, a Sysop reminder will begin appearing at program termination and will also be written to the current node's caller log file. 4.7 Revision history --------------------- Date Version Details -------- ------- ------- 03-29-92 1.0 PCBFX initial release. 04-03-92 1.1 See the enclsoed file FEATURES.NEW. 5.0 Registering PCBFX ---------------------- Registration removes the [UNREGISTERED COPY] message at program termination along with the corresponding brief delay which provides a seamless interface with the PCBoard BBS software. Registration is $15.00 and may be paid by check, money order, VISA, Mastercard, Discover, and American Express. Receive a registration number INSTANTLY by registering with a major credit card! Refer to the ORDER.FRM file for complete registration instructions. -------------------------------------------------------------------- Page 18 PCBFX Page 18 -------------------------------------------------------------------- 5.1 Register with CONFIDENCE - Author Information -------------------------------------------------- L. Brent Yandell has been programming for over eleven years, with more than five years of developing telecommunications software. Many Sysops will be familiar with PCBFV: the popular on-line PCBoard File Viewer, QReader: the `full-screen' text door, and ChatBox: the split-screen Sysop-chat\caller-page door. Yandell Computer Services (YCS) is a licensed business, operating and existing under the laws of the State of Florida. Writing BBS Shareware doors and utilities, in addition to custom programming, is our business.... our ONLY business. First Door Release: 7/6/87 (USBBSDOR) - Still updated and supported! YCS Shareware is GUARANTEED (each product's documentation contains each product's specific guarantee). Yandell Computer Services is an *AUTHORIZED* merchant for VISA, Mastercard, Discover, and American Express charge cards. A dedicated multi-node BBS for support and on-line registrations, a toll-free voice line for registrations, and a voice support line for registered customers are just a few of the offerings in our effort to provide you with FAST, FRIENDLY SERVICE.